Parts • Full • Next ▶

Frequently asked questions about Reticulum and RNode.

• What's the current status?

• So what is …

• How does routing work without authoritative systems?

• How secure is Reticulum?

• Short version

• Long version

• What do you mean by forward secret?

• What’s the legality of the system?

• Why don’t all nodes route data by default?

• What’s to stop someone from flooding the network?

• What’s to stop someone from flooding the radio to prevent communication?

• What are the system requirements for running a Reticulum node?

• What RNode LoRa transceiver should I buy?

• What is the range of an RNode?

• What is the power consumption of an RNode?

• How does RNode deal with duty cycle limits?

• Why won’t my TX Power go over 17 / Radio State Mismatch

• References

From Current Status ↗ in the manual:

All core protocol features are implemented and functioning, but additions will probably occur as real-world use is explored. The API and wire-format can be considered complete and stable, but could change if absolutely warranted. The Python code, for which this documentation is written, and known as the Reticulum Network Stack, is the Reference Implementation of Reticulum. The Reticulum Protocol is defined entirely and authoritatively by this reference implementation, and this manual. It is maintained by Mark Qvist, identified by the Reticulum Identity <bc7291552be7a58f361522990465165c>.

No. Mark stepped back from public-facing support and online community interaction in December 2025cite-ref-1[1], but he is still actively developing Reticulum and related projects elsewhere.

Development of the reference implementation and related projects happens over Reticulum with rngit. New releases are published on Aleph and PyPI. The GitHub repositories are only public mirrors that receive irregular updates.

Parts • Full • Next ▶